Prev Next

Print

This section describes known issues with the current release of Sitecore V5.1.

1.1.  Safe Mode

Sitecore does not work in the Safe Mode since IIS is unavailable in such case.

1.2.  Odd Entries in Logfiles

The following messages may appear in Sitecore log files:

2888 14:37:20 WARN  Could not find type in ReflectionUtil.CreateObject: Sitecore.Web.UI.HtmlControls.ShellImage
2888 14:37:20 WARN  Could not find type in ReflectionUtil.CreateObject: Sitecore.Web.UI.HtmlControls.ShellImage
2888 14:37:20 WARN  Could not find type in ReflectionUtil.CreateObject: Sitecore.Web.UI.HtmlControls.ShellImage
...

This is not a bug or error - just messages for administrator's information.

1.3.  JavaScript error in Layout Studio

Open any layout, click on a placeholder twice, then click OK. As a result, JavaScript error occurs and the placeholder appearance becomes broken.

However, you can continue your work, the changes are saved.

1.4.  Underscore and Dash Reserved

Underscore ('_') and dash ('-') are reserved characters and cannot be used in encodeNameReplacements.

For instance, the following replace pattern entails disappearing of some content node tabs:

  <replace mode="on" find=" " replaceWith="_" />

  or

  <replace mode="on" find=" " replaceWith="-" />

As a workaround, you have to define the replace string with other characters.  For instance:

 <replace mode="on" find=" " replaceWith=",-sp-," />

1.5.  XPath "//" Performance

The use of XPath expressions with the double forward slash (//) in the XSLT renderings causes slow performance.  A bug in the Microsoft .Net XML object can cause performance problems when getting items based on the items ID. The problem will show itself as the first item lookup taking an unreasonable long time (1,000+ ms) whereas lookups hereafter execute quickly. This can be spotted using the trace or profile options.

For example:

  <xsl:for-each select="$home/item[@key='news']/item[@key='news archive']//item">

When getting an item based on the ID, Sitecore makes a lookup on /sitecore/content//[@id]. For some inexplicable reason, this is extremely slow. Replaced with //[@id] this operation takes 20ms or less to execute for the first instance and 1ms or less for succeeding instances. This is contrary to all logic, qualifying the Xpath statement should make the search execute faster, as only a subset of the tree is searched.

Developers should observe this issue when they write XPath statements.

Note that if you use a variable in XSLT, e.g.

<xsl:variable name=”foo” select=”//item[@id=’23432’]/>

the XPATH corresponding to the variable will be evaluated every time the variable is accessed (i.e. a sort of macro substitution). This will obviously result in hopeless performance when used with //. Therefore, write your variables in full, e.g:

<xsl:variable name=”foo” select=”/item[...]/item[...]/item[..]item[@id=’23432’]/>

This can easily boost your performance significantly. Again, you can also use trace and profile to spot performance issues in your own XSLTs.

1.6.  Error in Log file after IIS Restart

After IIS restart and further uploading, the following error may appear in the LOG file:

1.7.  contentStartItem web.config parameter does not work

contentStartItem web.config parameter does not work in Sitecore up to 5.2. If you need to set an item that should be selected first when Content Editor is started you should use the Default Item field for a certain user in User Manager. So, this is only possible on per user basis so far.

1.8.  Apply Button Title

The buttons with "Apply" title have changed their title to "Bruk".

Please use this package to fix this issue.

1.9.  Renaming a User

Renaming a user in User Manager when the details view is selected throws JavaScript error.

Prev

Next